improvement: Use UV as the default installer for Kraken build-time virtual environments #281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rtual environments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This MR switches to UV as the default installer for Kraken-wrapper runtime virtual environments. UV-support in Kraken has been in testing for a while and has shown great promise, reducing installation times of virtual environments by at least one magnitude.
We depend on the
uvpackage directly already so this should just work out of the box for everyone that picks up the latestkraken-wrapperversion. Existing virtual environments will continue to use the same installer as the information on the installer used is written into the virtual environment and re-used on upgrades/reinstalls.